opencode-onboard 0.1.3 → 0.1.5

package/content/.agents/agents/back-engineer.md

@@ -72,3 +72,10 @@ Rules:
 **Files changed:** <list>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | back-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | back-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | back-engineer | completed | {files changed count} files |`

package/content/.agents/agents/devops-manager.md

@@ -56,10 +56,11 @@ Rules:
 1. Verify all changes are on a feature branch, never `main`
 2. Load the matching pullrequest skill
 3. Capture screenshots of local running app if UI changes exist
-4. Commit and push the feature branch
-5. Create the PR following the skill instructions
-6. Post PR comment with screenshots and change summary
-7. Report PR URL to the lead
+4. Read `.agents/session-log.md` if it exists — include a "Session Activity" section in the PR description with agent names, task counts, and total duration
+5. Commit and push the feature branch
+6. Create the PR following the skill instructions
+7. Post PR comment with screenshots and change summary
+8. Report PR URL to the lead
 
 ### Feedback Mode (PR review loop)
 1. Load the matching pullrequest observer skill
@@ -106,3 +107,10 @@ Rules:
 **Questions for human:** <count>, <list>
 **Acknowledged only:** <count>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | devops-manager | started | {mode} mode |`
+- On skill load: `| {ISO timestamp} | devops-manager | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | devops-manager | completed | {summary} |`

package/content/.agents/agents/front-engineer.md

@@ -71,3 +71,10 @@ Rules:
 **Files changed:** <list>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | front-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | front-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | front-engineer | completed | {files changed count} files |`

package/content/.agents/agents/infra-engineer.md

@@ -72,3 +72,10 @@ Rules:
 **Resources affected:** <list>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | infra-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | infra-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | infra-engineer | completed | {files changed count} files |`

package/content/.agents/agents/quality-engineer.md

@@ -72,3 +72,10 @@ Rules:
 **Acceptance criteria:** met | <unmet items>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | quality-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | quality-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | quality-engineer | completed | {tests added count} tests |`

package/content/.agents/agents/security-auditor.md

@@ -82,3 +82,10 @@ Rules:
 
 **Blockers:** none | <critical findings that must be resolved before PR>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | security-auditor | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | security-auditor | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | security-auditor | completed | {findings count} findings |`

package/content/.agents/skills/browser-automation/SKILL.md

@@ -1,19 +1,17 @@
 ---
 name: browser-automation
-description: Reliable, composable browser automation using minimal OpenCode Browser primitives.
+description: Reliable, composable browser automation using OpenCode Browser primitives. Use when capturing screenshots of a locally running app, clicking UI elements, reading page content, or automating browser interactions on localhost.
 license: MIT
-compatibility: opencode
+compatibility: Requires opencode-browser extension installed and running.
 metadata:
-  audience: agents
-  domain: browser
+  author: copilots
+  version: "1.0"
 ---
 
-## What I do
+Browser MCP tools are permitted ONLY for interactions with the LOCAL running app on `localhost` URLs.
+**Navigating to external services (github.com, dev.azure.com, etc.) via browser MCP is FORBIDDEN.**
 
-- Provide a safe, composable workflow for browsing tasks
-- Use `browser_query` list and index selection to click reliably
-- Confirm state changes after each action
-- Support CLI-first debugging with `opencode-browser tool` commands
+---
 
 ## Best-practice workflow
 
@@ -25,6 +23,8 @@ metadata:
 6. Click, type, or select using `index`
 7. Confirm using `browser_query` or `browser_snapshot`
 
+---
+
 ## CLI-first debugging
 
 - List all available tools: `npx @different-ai/opencode-browser tools`
@@ -33,7 +33,7 @@ metadata:
 - Run smoke test: `npx @different-ai/opencode-browser self-test`
 - After `update`, reload the unpacked extension in `chrome://extensions`
 
-This path is useful for reproducing selector/scroll issues quickly before running a full OpenCode session.
+---
 
 ## Selecting options
 
@@ -41,6 +41,8 @@ This path is useful for reproducing selector/scroll issues quickly before runnin
 - Prefer `value` or `label`; use `optionIndex` when needed
 - Example: `browser_select({ selector: "select", value: "plugin" })`
 
+---
+
 ## Query modes
 
 - `text`: read visible text from a matched element
@@ -49,11 +51,15 @@ This path is useful for reproducing selector/scroll issues quickly before runnin
 - `exists`: check presence and count
 - `page_text`: extract visible page text
 
+---
+
 ## Opening tabs
 
 - Use `browser_open_tab` to create a new tab, optionally with `url` and `active`
 - Example: `browser_open_tab({ url: "https://example.com", active: false })`
 
+---
+
 ## Troubleshooting
 
 - If a selector fails, run `browser_query` with `mode=page_text` to confirm the content exists
@@ -61,3 +67,13 @@ This path is useful for reproducing selector/scroll issues quickly before runnin
 - For inbox/chat panes, try text selectors first (`text:Subject line`) then verify selection with `browser_query`
 - For scrollable containers, pass both `selector` and `x`/`y` to `browser_scroll` and then verify `scrollTop`
 - Confirm results after each action
+
+---
+
+## Guardrails
+
+- ✅ Screenshots of locally running app on `localhost` URLs
+- ✅ Click, type, scroll, query on `localhost` pages
+- ❌ Navigate to external services (github.com, dev.azure.com, npmjs.com, etc.) — FORBIDDEN
+- ❌ Use browser tools for any DevOps or GitHub operations — FORBIDDEN
+- ❌ Use browser tools to read or modify production systems — FORBIDDEN

package/content/.agents/skills/ob-pullrequest-az/SKILL.md

@@ -0,0 +1,170 @@
+---
+name: ob-pullrequest-az
+description: Create Azure DevOps PRs with screenshots, or read and triage PR review feedback. Use when shipping a feature branch or when user says "I've added comments to the PR".
+license: MIT
+compatibility: Requires az CLI, az devops extension, openspec CLI, and opencode-browser for screenshots.
+metadata:
+  author: copilots
+  version: "1.0"
+---
+
+**RTK - MANDATORY**
+
+Use `rtk` wrapper for ALL CLI commands:
+- `rtk git add` NOT `git add`
+- `rtk git commit` NOT `git commit`
+- `rtk git push` NOT `git push`
+- `rtk az repos pr create` NOT `az repos pr create`
+- `rtk az repos pr work-item add` NOT `az repos pr work-item add`
+- `rtk az devops invoke` NOT `az devops invoke`
+
+**Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
+Browser tools are ONLY permitted for screenshots of the LOCAL running app on `localhost` URLs.
+
+---
+
+## Mode A: Create PR (ship mode)
+
+Triggered when devops-manager is in ship mode after implementation is complete.
+
+### Step 1: Verify feature branch
+
+```bash
+rtk git branch --show-current
+```
+
+Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
+
+### Step 2: Capture screenshots (if UI changes exist)
+
+```bash
+browser_navigate url="http://localhost:{port}/{route}"
+browser_wait ms=2000
+browser_screenshot
+```
+
+Save to: `openspec/changes/{change-name}/images/{feature}.png`
+
+### Step 3: Commit and push
+
+```bash
+rtk git add .
+rtk git commit -m "feat(#{id}): {description}"
+rtk git push origin feature/{id}-{slug}
+```
+
+### Step 4: Create PR
+
+```bash
+rtk az repos pr create \
+  --repository {repo} \
+  --source-branch feature/{id}-{slug} \
+  --target-branch main \
+  --title "feat(#{id}): {title}" \
+  --description "{description}"
+```
+
+### Step 5: Link work item (MANDATORY, run sequentially — not in parallel)
+
+```bash
+rtk az repos pr work-item add --id {pr-id} --work-items {workitem-id}
+```
+
+### Step 6: Post screenshot comment
+
+Build raw URL for each image:
+```
+https://dev.azure.com/{org}/{project}/_apis/git/repositories/{repo}/items?path=openspec/changes/{change}/images/{file}.png&versionType=branch&version={branch}&api-version=7.1
+```
+
+Post via:
+```bash
+rtk az devops invoke \
+  --area git --resource pullRequestThreads \
+  --route-parameters project={project} repositoryId={repo} pullRequestId={pr-id} \
+  --http-method POST --api-version 7.1 --in-file body.json
+```
+
+`body.json`:
+```json
+{
+  "comments": [{
+    "parentCommentId": 0,
+    "content": "## Screenshots\n\n![{feature}]({raw-url})",
+    "commentType": 1
+  }],
+  "status": "active"
+}
+```
+
+---
+
+## Mode B: Read PR Feedback (feedback mode)
+
+Triggered when user says "I've added comments to the PR" or "check PR feedback".
+
+### Step 1: Find PRs
+
+If PR link provided, extract ID from URL. Otherwise:
+```bash
+rtk az repos pr list --repository {repo} --status active --top 1
+```
+
+### Step 2: Read comment threads
+
+```bash
+rtk az devops invoke \
+  --area git --resource pullRequestThreads \
+  --route-parameters project={project} repositoryId={repo} pullRequestId={id} \
+  --http-method GET --api-version 7.1
+```
+
+### Step 3: Categorize feedback
+
+| Category | Description | Action |
+|----------|-------------|--------|
+| `code-change` | Reviewer requests code modification | Return to lead to spawn specialists |
+| `spec-update` | Affects proposal, design, or tasks | Update openspec artifacts |
+| `question` | Reviewer asks a question | Reply with answer |
+| `resolved` | Thread already resolved | Skip |
+
+### Step 4: Update openspec (if spec-update)
+
+```bash
+rtk git branch --show-current
+# feature/193208-roles-crud → change: us-193208-roles-crud
+```
+
+Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as appropriate.
+
+### Step 5: Reply to each thread
+
+```bash
+rtk az devops invoke \
+  --area git --resource pullRequestThreadComments \
+  --route-parameters project={project} repositoryId={repo} pullRequestId={id} threadId={tid} \
+  --http-method POST --api-version 7.1 --in-file reply.json
+```
+
+`reply.json`:
+```json
+{
+  "comments": [{
+    "parentCommentId": 1,
+    "content": "Acknowledged — applying this change now.",
+    "commentType": 1
+  }]
+}
+```
+
+---
+
+## Guardrails
+
+- ✅ Commit and push to feature branches only
+- ✅ Create and comment on PRs via az CLI
+- ✅ Screenshots of localhost only via browser_screenshot
+- ❌ Commit or push to `main` — FORBIDDEN
+- ❌ Force push — FORBIDDEN
+- ❌ Merge or approve PRs — human-only
+- ❌ Navigate browser to dev.azure.com — FORBIDDEN

package/content/.agents/skills/ob-pullrequest-gh/SKILL.md

@@ -0,0 +1,140 @@
+---
+name: ob-pullrequest-gh
+description: Create GitHub PRs with screenshots, or read and triage PR review feedback. Use when shipping a feature branch or when user says "I've added comments to the PR".
+license: MIT
+compatibility: Requires gh CLI, openspec CLI, and opencode-browser for screenshots.
+metadata:
+  author: copilots
+  version: "1.0"
+---
+
+**RTK - MANDATORY**
+
+Use `rtk` wrapper for ALL CLI commands:
+- `rtk git add` NOT `git add`
+- `rtk git commit` NOT `git commit`
+- `rtk git push` NOT `git push`
+- `rtk gh pr create` NOT `gh pr create`
+- `rtk gh pr comment` NOT `gh pr comment`
+- `rtk gh api` NOT `gh api`
+
+**Browser MCP tools are FORBIDDEN for all GitHub operations.**
+Browser tools are ONLY permitted for screenshots of the LOCAL running app on `localhost` URLs.
+
+---
+
+## Mode A: Create PR (ship mode)
+
+Triggered when devops-manager is in ship mode after implementation is complete.
+
+### Step 1: Verify feature branch
+
+```bash
+rtk git branch --show-current
+```
+
+Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
+
+### Step 2: Capture screenshots (if UI changes exist)
+
+```bash
+browser_navigate url="http://localhost:{port}/{route}"
+browser_wait ms=2000
+browser_screenshot
+```
+
+Save to: `openspec/changes/{change-name}/images/{feature}.png`
+
+### Step 3: Commit and push
+
+```bash
+rtk git add .
+rtk git commit -m "feat(#{id}): {description}"
+rtk git push origin feature/{slug}
+```
+
+### Step 4: Create PR
+
+```bash
+rtk gh pr create \
+  --base main \
+  --head feature/{slug} \
+  --title "feat: {title}" \
+  --body "{description}"
+```
+
+### Step 5: Post screenshot comment
+
+Build raw URL for each image:
+```
+https://raw.githubusercontent.com/{owner}/{repo}/feature/{slug}/openspec/changes/{change}/images/{file}.png
+```
+
+Post comment:
+```bash
+rtk gh pr comment {pr-number} --body $'## Screenshots\n\n![{feature}]({raw-url})'
+```
+
+---
+
+## Mode B: Read PR Feedback (feedback mode)
+
+Triggered when user says "I've added comments to the PR" or "check PR feedback".
+
+### Step 1: Find PRs
+
+If PR link provided, extract number from URL. Otherwise:
+```bash
+rtk gh pr list --state open --limit 1
+```
+
+### Step 2: Read comment threads
+
+```bash
+rtk gh pr view {pr-number} --comments
+# Or structured output:
+rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/comments
+rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
+```
+
+### Step 3: Categorize feedback
+
+| Category | Description | Action |
+|----------|-------------|--------|
+| `code-change` | Reviewer requests code modification | Return to lead to spawn specialists |
+| `spec-update` | Affects proposal, design, or tasks | Update openspec artifacts |
+| `question` | Reviewer asks a question | Reply with answer |
+| `resolved` | Thread already resolved | Skip |
+
+### Step 4: Update openspec (if spec-update)
+
+```bash
+rtk git branch --show-current
+# feature/add-user-auth → change: add-user-auth
+```
+
+Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as appropriate.
+
+### Step 5: Reply to each comment thread
+
+```bash
+# Reply to a review comment
+rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
+  --method POST \
+  --field body="Acknowledged — applying this change now."
+
+# Or post a general PR comment
+rtk gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
+```
+
+---
+
+## Guardrails
+
+- ✅ Commit and push to feature branches only
+- ✅ Create and comment on PRs via gh CLI
+- ✅ Screenshots of localhost only via browser_screenshot
+- ❌ Commit or push to `main` — FORBIDDEN
+- ❌ Force push — FORBIDDEN
+- ❌ Merge or approve PRs — human-only
+- ❌ Navigate browser to github.com — FORBIDDEN

package/content/.agents/skills/ob-userstory-az/SKILL.md

@@ -1,206 +1,172 @@
----
-name: ob-userstory-az
-description: Parse Azure DevOps user story URL and create OpenSpec change. Use when user provides an Azure DevOps URL.
-license: MIT
-compatibility: Requires openspec CLI and Azure CLI.
-metadata:
-  author: copilots
-  version: "3.0"
----
-
-**RTK - MANDATORY**
-
-Use `rtk` wrapper for ALL CLI commands:
-- `rtk az boards work-item show` NOT `az boards work-item show`
-- `rtk openspec new change` NOT `openspec new change`
-
-**Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
-
----
-
-## Azure CLI Setup (One-Time)
-
-```bash
-az config set extension.dynamic_install_allow_preview=true
-az extension add --name azure-devops
-az login
-az devops login --organization https://dev.azure.com/plainconcepts
-```
-
-**PAT Token**, go to `https://dev.azure.com/plainconcepts/_usersSettings/tokens`
-Create with scopes: **Work Items (Read & Write)** + **Code (Read & Write)**
-
----
-
-## Steps
-
-1. **Extract Work Item ID** from URL
-   - `?workitem=193208` → ID: 193208
-   - `/workitems/edit/193208` → ID: 193208
-
-2. **Fetch Work Item**
-   ```bash
-   rtk az boards work-item show --id 193208
-   ```
-   Do NOT use `--organization` flag (uses default org).
-
-3. **Extract Key Fields** from JSON response:
-   - `fields.System.Title` → Title
-   - `fields.System.Description` → Description (may be HTML, strip tags)
-   - `fields.System.WorkItemType` → Type
-   - `fields.System.IterationPath` → Sprint
-   - `fields.System.State` → State
-   - `fields.System.AcceptanceCriteria` → AC (if present)
-
-4. **Create OpenSpec Change**
-   ```bash
-   rtk openspec new change "us-{id}-{slug}"
-   ```
-
----
-
-## Full Azure DevOps CLI Reference
-
-Use these for ALL DevOps operations, browser MCP is FORBIDDEN.
-
-### Work Items
-```bash
-# Read work item
-rtk az boards work-item show --id <id>
-
-# Update work item state
-rtk az boards work-item update --id <id> --state "Active"
-```
-
-### Pull Requests
-```bash
-# List open PRs
-rtk az repos pr list --repository <repo> --status active --top 5
-
-# Show PR details
-rtk az repos pr show --id <pr-id>
-
-# Create PR
-rtk az repos pr create \
-  --repository <repo> \
-  --source-branch feature/<id>-<slug> \
-  --target-branch main \
-  --title "feat(#<id>): <title>" \
-  --description "<description>"
-
-# Update PR description
-rtk az repos pr update --id <pr-id> --description "<text>"
-
-# Link work item to PR (run sequentially, not parallel)
-rtk az repos pr work-item add --id <pr-id> --work-items <work-item-id>
-```
-
-### PR Threads (Comments)
-```bash
-# Read all threads
-rtk az devops invoke \
-  --area git --resource pullRequestThreads \
-  --route-parameters project=PlainConcepts.CapacityTool repositoryId=<repo> pullRequestId=<id> \
-  --http-method GET --api-version 7.1
-
-# Post new comment thread (requires body.json)
-rtk az devops invoke \
-  --area git --resource pullRequestThreads \
-  --route-parameters project=PlainConcepts.CapacityTool repositoryId=<repo> pullRequestId=<id> \
-  --http-method POST --api-version 7.1 --in-file body.json
-
-# Reply to existing thread
-rtk az devops invoke \
-  --area git --resource pullRequestThreadComments \
-  --route-parameters project=PlainConcepts.CapacityTool repositoryId=<repo> pullRequestId=<id> threadId=<tid> \
-  --http-method POST --api-version 7.1 --in-file reply.json
-```
-
-### Comment Body JSON format
-```json
-{
-  "comments": [
-    {
-      "parentCommentId": 0,
-      "content": "Your markdown comment here.",
-      "commentType": 1
-    }
-  ],
-  "status": "active"
-}
-```
-
-For replies, `parentCommentId` should be the ID of the first comment in the thread (usually 1).
-
----
-
-## Screenshot / Image Strategy
-
-**Never upload images as PR attachments.** Save to openspec change folder and reference via raw URL.
-
-### Save location
-```
-openspec/changes/{change-name}/images/{screenshot}.png
-```
-
-### Raw URL format (renders inline in PR comments)
-```
-https://dev.azure.com/plainconcepts/PlainConcepts.CapacityTool/_apis/git/repositories/{repo}/items?path=openspec/changes/{change}/images/{file}.png&versionType=branch&version={branch}&api-version=7.1
-```
-
-Do NOT use `_git/` URLs, they return HTML, not raw binary.
-
-### PR comment with screenshot
-```json
-{
-  "comments": [
-    {
-      "parentCommentId": 0,
-      "content": "## Screenshots\n\n![Description](https://dev.azure.com/plainconcepts/PlainConcepts.CapacityTool/_apis/git/repositories/{repo}/items?path=openspec/changes/{change}/images/{file}.png&versionType=branch&version={branch}&api-version=7.1)",
-      "commentType": 1
-    }
-  ],
-  "status": "active"
-}
-```
-
----
-
-## URL Formats Reference
-
-```
-# Sprint board with work item
-https://dev.azure.com/{org}/{project}/_sprints/backlog/{team}/{project}/Sprint%20110?workitem=193208
-
-# Direct work item
-https://dev.azure.com/{org}/{project}/_workitems/edit/193208
-
-# PR
-https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{pr-id}
-```
-
----
-
-## Output Format
-
-```
-## User Story Parsed
-
-**Work Item:** #193208
-**Title:** Roles CRUD
-**Type:** User Story
-**Iteration:** Sprint 110
-**State:** New
-
-**Change Created:** us-193208-roles-crud
-
-### Next Steps
-1. Review the proposal
-2. Say "implement the plan" to start implementation
-```
-
-## Constraints
-
-- This skill only PARSES and PROPOSES, implementation via openspec-apply-change
-- Always use `rtk` for CLI commands
-- Browser MCP tools FORBIDDEN for all DevOps operations
+---
+name: ob-userstory-az
+description: Parse Azure DevOps user story URL and create OpenSpec change. Use when user provides an Azure DevOps URL.
+license: MIT
+compatibility: Requires openspec CLI and Azure CLI.
+metadata:
+  author: copilots
+  version: "3.1"
+---
+
+**RTK - MANDATORY**
+
+Use `rtk` wrapper for ALL CLI commands:
+- `rtk az boards work-item show` NOT `az boards work-item show`
+- `rtk openspec new change` NOT `openspec new change`
+
+**Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
+
+---
+
+## Azure CLI Setup (One-Time)
+
+```bash
+az config set extension.dynamic_install_allow_preview=true
+az extension add --name azure-devops
+az login
+az devops login --organization https://dev.azure.com/{org}
+```
+
+**PAT Token**, go to `https://dev.azure.com/{org}/_usersSettings/tokens`
+Create with scopes: **Work Items (Read & Write)** + **Code (Read & Write)**
+
+---
+
+## Steps
+
+1. **Extract Work Item ID** from URL
+   - `?workitem=193208` → ID: 193208
+   - `/workitems/edit/193208` → ID: 193208
+
+2. **Fetch Work Item**
+   ```bash
+   rtk az boards work-item show --id 193208
+   ```
+   Do NOT use `--organization` flag (uses default org).
+
+3. **Extract Key Fields** from JSON response:
+   - `fields.System.Title` → Title
+   - `fields.System.Description` → Description (may be HTML, strip tags)
+   - `fields.System.WorkItemType` → Type
+   - `fields.System.IterationPath` → Sprint
+   - `fields.System.State` → State
+   - `fields.System.AcceptanceCriteria` → AC (if present)
+
+4. **Create OpenSpec Change**
+   ```bash
+   rtk openspec new change "us-{id}-{slug}"
+   ```
+
+---
+
+## Full Azure DevOps CLI Reference
+
+Use these for ALL DevOps operations, browser MCP is FORBIDDEN.
+
+### Work Items
+```bash
+# Read work item
+rtk az boards work-item show --id <id>
+
+# Update work item state
+rtk az boards work-item update --id <id> --state "Active"
+```
+
+### PR Threads (Comments)
+```bash
+# Read all threads
+rtk az devops invoke \
+  --area git --resource pullRequestThreads \
+  --route-parameters project={project} repositoryId=<repo> pullRequestId=<id> \
+  --http-method GET --api-version 7.1
+
+# Post new comment thread (requires body.json)
+rtk az devops invoke \
+  --area git --resource pullRequestThreads \
+  --route-parameters project={project} repositoryId=<repo> pullRequestId=<id> \
+  --http-method POST --api-version 7.1 --in-file body.json
+
+# Reply to existing thread
+rtk az devops invoke \
+  --area git --resource pullRequestThreadComments \
+  --route-parameters project={project} repositoryId=<repo> pullRequestId=<id> threadId=<tid> \
+  --http-method POST --api-version 7.1 --in-file reply.json
+```
+
+### Comment Body JSON format
+```json
+{
+  "comments": [
+    {
+      "parentCommentId": 0,
+      "content": "Your markdown comment here.",
+      "commentType": 1
+    }
+  ],
+  "status": "active"
+}
+```
+
+For replies, `parentCommentId` should be the ID of the first comment in the thread (usually 1).
+
+---
+
+## Screenshot / Image Strategy
+
+**Never upload images as PR attachments.** Save to openspec change folder and reference via raw URL.
+
+### Save location
+```
+openspec/changes/{change-name}/images/{screenshot}.png
+```
+
+### Raw URL format (renders inline in PR comments)
+```
+https://dev.azure.com/{org}/{project}/_apis/git/repositories/{repo}/items?path=openspec/changes/{change}/images/{file}.png&versionType=branch&version={branch}&api-version=7.1
+```
+
+Do NOT use `_git/` URLs, they return HTML, not raw binary.
+
+---
+
+## URL Formats Reference
+
+```
+# Sprint board with work item
+https://dev.azure.com/{org}/{project}/_sprints/backlog/{team}/{project}/Sprint%20110?workitem=193208
+
+# Direct work item
+https://dev.azure.com/{org}/{project}/_workitems/edit/193208
+
+# PR
+https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{pr-id}
+```
+
+---
+
+## Output Format
+
+```
+## User Story Parsed
+
+**Work Item:** #{id}
+**Title:** {title}
+**Type:** User Story
+**Iteration:** {sprint}
+**State:** {state}
+
+**Change Created:** us-{id}-{slug}
+
+### Next Steps
+1. Review the proposal
+2. Say "implement the plan" to start implementation
+```
+
+---
+
+## Guardrails
+
+- ✅ Parse Azure DevOps URL and create OpenSpec change
+- ✅ Use `rtk` for all Azure CLI operations
+- ❌ Browser MCP tools for Azure DevOps operations — FORBIDDEN
+- ❌ Implementation — this skill only parses and proposes

package/content/.agents/skills/ob-userstory-gh/SKILL.md

@@ -5,9 +5,17 @@ license: MIT
 compatibility: Requires openspec CLI and gh CLI.
 metadata:
   author: copilots
-  version: "1.0"
+  version: "1.1"
 ---
 
+**RTK - MANDATORY**
+
+Use `rtk` wrapper for ALL CLI commands:
+- `rtk gh issue view` NOT `gh issue view`
+- `rtk gh issue list` NOT `gh issue list`
+- `rtk gh issue edit` NOT `gh issue edit`
+- `rtk openspec new change` NOT `openspec new change`
+
 **Browser MCP tools are FORBIDDEN for all GitHub operations.**
 
 ---
@@ -33,7 +41,7 @@ gh auth status
 
 2. **Fetch Issue**
    ```bash
-   gh issue view 42 --json number,title,body,labels,milestone,state
+   rtk gh issue view 42 --json number,title,body,labels,milestone,state
    ```
 
 3. **Extract Key Fields** from JSON response:
@@ -46,7 +54,7 @@ gh auth status
 
 4. **Create OpenSpec Change**
    ```bash
-   openspec new change "gh-{number}-{slug}"
+   rtk openspec new change "gh-{number}-{slug}"
    ```
 
 ---
@@ -58,55 +66,13 @@ Use these for ALL GitHub operations, browser MCP is FORBIDDEN.
 ### Issues
 ```bash
 # Read issue
-gh issue view <number>
+rtk gh issue view <number>
 
 # List open issues
-gh issue list --state open --limit 10
+rtk gh issue list --state open --limit 10
 
 # Update issue
-gh issue edit <number> --add-label "in-progress"
-```
-
-### Pull Requests
-```bash
-# List open PRs
-gh pr list --state open
-
-# Show PR details
-gh pr view <number>
-
-# Create PR
-gh pr create \
-  --base main \
-  --head feature/{slug} \
-  --title "feat: <title>" \
-  --body "<description>"
-
-# Update PR
-gh pr edit <number> --body "<text>"
-```
-
-### PR Comments
-```bash
-# Read PR comments
-gh pr view <number> --comments
-
-# Post PR comment
-gh pr comment <number> --body "Your markdown comment here."
-
-# Reply to review comment via API
-gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
-  --method POST \
-  --field body="Reply text here."
-```
-
-### Review Comments (structured)
-```bash
-# Get all review comments on a PR
-gh api repos/{owner}/{repo}/pulls/{pr-number}/comments
-
-# Get all reviews
-gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
+rtk gh issue edit <number> --add-label "in-progress"
 ```
 
 ---
@@ -125,11 +91,6 @@ openspec/changes/{change-name}/images/{screenshot}.png
 https://raw.githubusercontent.com/{owner}/{repo}/{branch}/openspec/changes/{change}/images/{file}.png
 ```
 
-### PR comment with screenshot
-```bash
-gh pr comment <number> --body "## Screenshots\n\n![Description](https://raw.githubusercontent.com/{owner}/{repo}/feature/{slug}/openspec/changes/{change}/images/{file}.png)"
-```
-
 ---
 
 ## URL Formats Reference
@@ -164,8 +125,11 @@ https://raw.githubusercontent.com/{owner}/{repo}/{branch}/{path}
 2. Say "implement the plan" to start implementation
 ```
 
-## Constraints
+---
+
+## Guardrails
 
-- This skill only PARSES and PROPOSES, implementation via openspec-apply-change
-- Always use `gh` CLI for GitHub operations
-- Browser MCP tools FORBIDDEN for all GitHub operations
+- ✅ Parse GitHub Issue URL and create OpenSpec change
+- ✅ Use `rtk gh` for all GitHub CLI operations
+- ❌ Browser MCP tools for GitHub operations — FORBIDDEN
+- ❌ Implementation — this skill only parses and proposes

package/content/AGENTS.md

@@ -65,6 +65,72 @@ Replace the entire contents of this file (`AGENTS.md`) with everything below the
 
 ---
 
+### Step 4b, Patch opsx-apply for ensemble
+
+Read `.opencode/commands/opsx-apply.md`. Find the step that instructs the agent to **implement tasks directly** — it will contain phrases like "make the code changes", "implement tasks", "loop until done or blocked". This step tells the agent to write code itself.
+
+**Replace that step and everything after it** (completion output, pause output, guardrails, fluid workflow) with the following:
+
+```markdown
+6. **Implement via ensemble team**
+
+   NEVER implement tasks directly. Always delegate to specialists via ensemble.
+
+   a. Create feature branch if not already on one: `feature/{id}-{slug}`
+   b. Create team:
+      ```
+      team_create "<change-name>"
+      ```
+      Announce: "Team running. Monitor at http://localhost:4747/"
+
+   c. Spawn only what the tasks require (in parallel):
+      ```
+      team_spawn name:front   agent:front-engineer  → UI/frontend tasks
+      team_spawn name:back    agent:back-engineer   → backend/API tasks
+      team_spawn name:infra   agent:infra-engineer  → infra/pipeline tasks
+      ```
+      Pass each specialist: their relevant tasks + all context file paths from step above.
+      Log each spawn to `.agents/session-log.md` (see Session Log section).
+
+   d. Wait for all → `team_results` → `team_shutdown` + `team_merge`
+
+7. **Quality check**
+
+   ```
+   team_spawn name:quality agent:quality-engineer
+   ```
+   Wait → `team_results` → fix blockers → `team_shutdown`
+
+8. **Mark tasks complete in openspec**
+
+   After specialists finish, update the tasks file: `- [ ]` → `- [x]` for each completed task.
+   Run `openspec status --change "<name>" --json` to confirm progress.
+
+9. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive with `/opsx-archive`
+   - If paused: explain why and wait for guidance
+
+   Then run `team_cleanup`.
+
+**Guardrails**
+- NEVER implement tasks directly — always use `team_create` + `team_spawn`
+- Always read context files before spawning (from the apply instructions output)
+- Always pass context file paths and task list to spawned specialists
+- Mark tasks complete in openspec AFTER specialists finish, not before
+- If task is ambiguous, pause and ask before spawning
+- If implementation reveals issues, pause and suggest artifact updates
+- Pause on errors, blockers, or unclear requirements — don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+```
+
+Keep all steps before the implementation step unchanged — they are openspec's domain (select change, check status, get instructions, read context, show progress).
+
+---
+
 ### Step 5, Confirm
 
 Tell the user:
@@ -108,9 +174,9 @@ This is the agent orchestration layer for your project. It provides:
 When the user provides a work item URL, says "implement the plan", or "I've added comments to the PR", **I own the full lifecycle**. I load the appropriate skill and use ensemble tools (`team_create`, `team_spawn`, etc.) to coordinate the agent team.
 
 Trigger patterns:
-- `work on this <azure-devops-url>` → spawn `devops-manager` in read mode → propose OpenSpec → implement → ship
-- `work on this <github-url>` → spawn `devops-manager` in read mode → propose OpenSpec → implement → ship
-- `implement the plan` → load skill `openspec-apply-change` → implement → ship
+- `work on this <azure-devops-url>` → spawn `devops-manager` in read mode → propose OpenSpec → **confirm with user** → implement → ship
+- `work on this <github-url>` → spawn `devops-manager` in read mode → propose OpenSpec → **confirm with user** → implement → ship
+- `implement the plan` → run `/opsx-apply` (ensemble orchestration is built into the command) → ship
 - `I've added comments to the PR` → spawn `devops-manager` in feedback mode → fix → update PR
 
 **Never delegate without a plan. Never write implementation code directly, always spawn specialists.**
@@ -166,21 +232,17 @@ devops-manager (ship mode)
 1. team_spawn devops-manager (read mode) → fetch work item via skill, output summary
 2. Load skill: openspec-propose → generate proposal.md, specs/, tasks.md
    - team_create → spawn design + specs in parallel → merge → write tasks.md
-3. Show summary, confirm with user before implementing
+3. Show the plan: change name, schema, total tasks, task list summary
+4. STOP. Ask user: "Ready to implement? (yes/no)" — DO NOT proceed until confirmed.
 ```
 
 ### Phase 2, Implement
 
 ```
-1. Load skill: openspec-apply-change → get apply instructions
-2. Create feature branch: feature/{id}-{slug}
-3. team_create "<change-name>"
-4. Announce: "Team running. Monitor at http://localhost:4747/"
-5. Spawn only what the task needs (in parallel):
-   team_spawn name:front   agent:front-engineer  → UI tasks
-   team_spawn name:back    agent:back-engineer   → backend tasks
-   team_spawn name:infra   agent:infra-engineer  → infra tasks
-6. Wait for all → team_results → team_shutdown + team_merge
+1. Run /opsx-apply (or load skill openspec-apply-change)
+   The command handles context reading, ensemble orchestration, and task marking automatically.
+   DO NOT implement tasks directly — the command spawns specialists via ensemble.
+2. After /opsx-apply completes, proceed to quality check.
 ```
 
 ### Phase 3, Quality
@@ -247,6 +309,7 @@ Skills are located in `.agents/skills/`. Each skill has a `SKILL.md` with a desc
 | `openspec-propose` | Propose change artifacts (proposal, specs, tasks) |
 | `openspec-apply-change` | Implement change with agent team |
 | `openspec-archive-change` | Archive completed change |
+| `browser-automation` | Browser automation for localhost UI — screenshots, clicks, queries |
 
 ---
 
@@ -276,6 +339,52 @@ Example: `feature/42-add-user-auth`
 
 ---
 
+## Session Log
+
+<!-- session-logging: enabled -->
+
+All agents MUST log their activity to `.agents/session-log.md`. This file is gitignored and temporary.
+
+**Check before logging:** Read the `session-logging` comment above. If it says `disabled`, skip all logging.
+
+**On first write per session**, create the file with the header:
+```markdown
+# Session Log
+
+| Timestamp | Agent | Action | Detail |
+|-----------|-------|--------|--------|
+```
+
+**Log these events** by appending a row:
+- Lead spawns an agent → `| {ISO timestamp} | lead | spawned | {agent-name} for {purpose} |`
+- Agent starts → `| {ISO timestamp} | {agent-name} | started | {task summary} |`
+- Agent loads a skill → `| {ISO timestamp} | {agent-name} | skill-loaded | {skill-name} |`
+- Agent completes → `| {ISO timestamp} | {agent-name} | completed | {files changed count} files |`
+- Agent blocked → `| {ISO timestamp} | {agent-name} | blocked | {reason} |`
+
+**Rules:**
+- Append only, never overwrite previous entries
+- One row per event, keep detail column short
+- Use ISO 8601 timestamps
+- The file is gitignored — never commit it
+
+---
+
+## RTK
+
+Use `rtk` wrapper for ALL CLI commands. Never run git, az, gh, or openspec commands directly.
+
+- `rtk git add` NOT `git add`
+- `rtk git commit` NOT `git commit`
+- `rtk git push` NOT `git push`
+- `rtk az boards work-item show` NOT `az boards work-item show`
+- `rtk az repos pr create` NOT `az repos pr create`
+- `rtk gh issue view` NOT `gh issue view`
+- `rtk gh pr create` NOT `gh pr create`
+- `rtk openspec new change` NOT `openspec new change`
+
+---
+
 ## Guardrails
 
 ### Git Operations

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-onboard",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Prepare any brownfield codebase for AI agent workflows using OpenCode, OpenSpec, and ensemble orchestration.",
   "keywords": [
     "opencode",